[PATCH 1/4] dnp3: check done state, not complete state for progress
authorJason Ish <jason.ish@oisf.net>
Tue, 6 Jan 2026 22:15:09 +0000 (16:15 -0600)
committerAndreas Dolp <dev@andreas-dolp.de>
Sun, 22 Feb 2026 12:28:52 +0000 (13:28 +0100)
commit33c884311d118b083f1be49421b1b6387a3a6462
treefe923530936a7b25addf6d8b753fa030b162f717
parent084b3724c690066e107b84e658ee4ad5644ebda3
[PATCH 1/4] dnp3: check done state, not complete state for progress

Complete is a flag used to tell if the message was completely parsed,
as not all messages may be completely parsed if we don't know all
their objects. However, they are still "done".

In the alstate-progress callback, check the done flag, not the
complete flag.

Ticket: #8181
(cherry picked from commit d61eef9a8a0d92921989479de15e5cbfec3251a9)

Origin: upstream, https://github.com/OISF/suricata/commit/63225d5f8ef64cc65164c0bb1800730842d54942.patch
Bug: https://redmine.openinfosecfoundation.org/issues/8181
Subject: Upstream fix for CVE-2026-22259 part 1

Gbp-Pq: Name CVE-2026-22259_1.patch
src/app-layer-dnp3.c